5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

WRITE


The WRITE statement writes a new record to the specified file.

  ?????   WRITE   ??? ?????????????????????? FAIL ?
  (1)             (2) (3)                        (4)

(1) T/F execution conditions
(2) Application ID
(3) File name or field name
(4) Fail action (0=nothing, 1=warning, 2=error, 3=cancel)

Sets True/False Status Indicator

If a record is written successfully, the current true/false status indicators are modified by setting the next indicator to T. If a write fails because of an ?Already on File? condition for a unique key in the file, the next indicator is set to F. In this case, the FAIL parameter determines what additional action to take. In addition, on a false condition, the predefined field STATUS CODE returns a token indicating the reason for an I/O command failure. This token can be used as a key to read the system message file to obtain a descriptive I/O error message (see STATUS CODE for details).

Using the Statement

When using this statement in conjunction with an RDBMS table, you can specify a field name instead of a file name to limit the volume of data being passed between APPX and the RDBMS. See the Partial-Record I/O section in Specifying Statements for more information.

Execution of the WRITE statement does not modify the position in the file for subsequent BEG READ/END READ or READNEXT operations.

Related Statements

DELETE, REWRITE

Example

In the following example, invoice batch control information is transferred to a file called EDIT. 

          CREATE   TAR EDIT       SHARE? Y  FAIL 0 CACHE NONE
          BEG READ TAR INVOICE1                HOLD 0 KEY IS  INVOICE1 KEY
          SET      TAR EDIT KEY                   =  TAR INVOICE1 KEY
          SET      TAR EDIT FILE NAME             =      INVC
          WRITE    TAR EDIT                  FAIL 0
  F       CANCEL   Unexpected Error WRITE TAR EDIT
          END READ TAR INVOICE1

Application Design Manual                                         "Powered by Appx Software"

713

©2006 By APPX Software, Inc. All Rights Reserved